Use full ephemeris data not 5min stat - #150
Conversation
|
@jzuhone - There is a good chance this will break the |
|
Is the interface impact then that after interpolation there may be small differences in ephemeris data used in the models? I had been thinking the 5 minute averages and 5 minute samples were the same but confess I did not explicitly check. |
|
Yes, I should have noted an interface impact. The ephemeris full data are at exactly 5 minute (300 sec) intervals while the stat data are "5min" 328 sec = 10 major frame intervals. So probably there will be small numerical diffs that show up if regression testing is down to floating point accuracy. |
|
And you hadn't asked for review yet - I just got excited about this one as it seemed a great no-impact fix! Still great if it is a super-tiny-impact fix. |
|
I did some testing and put the results in the description. |
Description
This allows running models that depend on the solar / orbit ephemeris files up to the limit of other CXC telemetry on all machines (not just HEAD).
There is an issue with cheta sync where the ephemeris 5min stats can lag behind other telemetry. This impacts GRETA machines and laptops that keep up to date with
cheta_sync.Interface impacts
Models like the ACIS FP model which depend on the ephemeris will change slightly. See below for an example.
Testing
Unit tests
Independent check of unit tests by Jean
Functional tests
Does it work
At this time, the cheta_sync ephem files go out through 2025:322. Without this PR, the following fails (
ValueError: Fetched telemetry does not span model start and stop times for orbitephem0_x), but with the PR it runs as expected.Model impact
For the ACIS FP model, here is a plot of the model difference between this PR and master.

